Automated connectivity to cloud resources

ABSTRACT

The present technology pertains to receiving a tag associating at least one routing domain in an on-premises site with at least one virtual network in a cloud environment associated with a cloud service provider. The present technology also pertains to the automation of populating route and propagation tables with the cloud service provider.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/390,239, filed on Jul. 30, 2021, entitled, “Automated Connectivity ToCloud Resources,” which in turn, claims priority to U.S. patentapplication No. 63/172,450, filed on Apr. 8, 2021, entitled “AutomatedWorkload Mapping of Cloud IaaS and Cloud Partner Interconnect,” thecontents of which are incorporated herein by reference in theirentirety.

DESCRIPTION OF THE RELATED TECHNOLOGY

The present technology relates in general to the field of computernetworking, and more particularly, to methods, systems, andnon-transitory computer-readable storage media for automatingconnectivity to cloud resources.

BACKGROUND

Enterprise networks often implement diverse and complex networktopologies to fulfill enterprise demands. The increasing diversity andcomplexity of such networks puts a greater strain on networkadministrators, and opens the door for more problems to occur, such aslower-than-desired uptime. Establishing and managing networkconnectivity can be very challenging and time-consuming for networkadministrators, and often result in lower guarantees for stable/accurateconnectivity, lower uptime, and/or lack of certain desirable features.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the various advantages andfeatures of the disclosure can be obtained, a more particulardescription of the principles briefly described above will be renderedby reference to specific embodiments thereof which are illustrated inthe appended drawings. Understanding that these drawings depict onlyexemplary embodiments of the disclosure and are not, therefore, to beconsidered to be limiting of its scope, the principles herein aredescribed and explained with additional specificity and detail throughthe use of the accompanying drawings in which:

FIG. 1 illustrates an example of a high-level network architecture inaccordance with some examples of the present disclosure;

FIG. 2 illustrates an example of a network topology in accordance withsome examples of the present disclosure;

FIG. 3 illustrates an example of a diagram showing the operation of aprotocol for managing an overlay network in accordance with someexamples of the present disclosure;

FIG. 4 illustrates an example of a diagram showing the operation ofvirtual private networks for segmenting a network in accordance withsome examples of the present disclosure;

FIG. 5 illustrates an example of a network capable of automatingconnectivity to cloud resources in accordance with some examples of thepresent disclosure;

FIGS. 6A-6C illustrate examples of graphical user interfaces (GUIs) fora network controller;

FIG. 7 is a flowchart of a method for automating connectivity to cloudresources in accordance with some examples of the present disclosure;and

FIG. 8 shows an example of a system for implementing certain aspects ofthe present technology;

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below.While specific implementations are discussed, it should be understoodthat this is done for illustration purposes only. A person skilled inthe relevant art will recognize that other components and configurationsmay be used without parting from the spirit and scope of the disclosure.Thus, the following description and drawings are illustrative and arenot to be construed as limiting. Numerous specific details are describedto provide a thorough understanding of the disclosure. However, incertain instances, well-known or conventional details are not describedin order to avoid obscuring the description. References to one or anembodiment in the present disclosure can be references to the sameembodiment or any embodiment; and, such references mean at least one ofthe embodiments.

Reference to “one embodiment” or “an embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment is included in at least one embodiment of the disclosure. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. Moreover, various features are described which may beexhibited by some embodiments and not by others.

The terms used in this specification generally have their ordinarymeanings in the art, within the context of the disclosure, and in thespecific context where each term is used. Alternative language andsynonyms may be used for any one or more of the terms discussed herein,and no special significance should be placed upon whether or not a termis elaborated or discussed herein. In some cases, synonyms for certainterms are provided. A recital of one or more synonyms does not excludethe use of other synonyms. The use of examples anywhere in thisspecification including examples of any terms discussed herein isillustrative only and is not intended to further limit the scope andmeaning of the disclosure or of any example term. Likewise, thedisclosure is not limited to various embodiments given in thisspecification.

Without intent to limit the scope of the disclosure, examples ofinstruments, apparatus, methods, and their related results according tothe embodiments of the present disclosure are given below. Note thattitles or subtitles may be used in the examples for the convenience of areader, which in no way should limit the scope of the disclosure. Unlessotherwise defined, technical and scientific terms used herein have themeaning as commonly understood by one of ordinary skill in the art towhich this disclosure pertains. In the case of conflict, the presentdocument, including definitions will control. Additional features andadvantages of the disclosure will be set forth in the description whichfollows, and in part will be obvious from the description, or can belearned by practice of the herein disclosed principles. The features andadvantages of the disclosure can be realized and obtained by means ofthe instruments and combinations particularly pointed out in theappended claims. These and other features of the disclosure will becomemore fully apparent from the following description and appended claimsor can be learned by the practice of the principles set forth herein.

Overview

The present technology provides methods, systems, and non-transitorycomputer-readable storage media are provided for automating connectivityto cloud resources.

An example method can include receiving a tag associating at least onerouting domain in an on-premises site with at least one virtual networkin a cloud environment associated with a cloud service provider (CSP).The method can also include configuring a virtual cross connect (VXC) ona software-defined wide-area network (SDWAN) router associated with asoftware-defined cloud infrastructure (SDCI) provider, the VXCconnecting the on-premises site to the cloud environment associated withthe CSP. The method can also include assigning border gateway protocol(BGP) parameters to the VXC. The method can also include configuring BGPpeering on a connectivity gateway in the cloud environment associatedwith the CSP. The method can also include connecting the connectivitygateway to the at least one virtual network in the cloud environment.The method can also include tagging the at least one virtual networkwith the tag. The method can also include configuring a connectionbetween the at least one routing domain in the on-premises site and theat least one virtual network in the cloud environment, wherein theconnection is based at least in part on the tag.

In some embodiments of the method, connecting the connectivity gatewayto the at least one virtual network can include invoking an API to usean interface associated with the SDCI provider. The method can alsoinclude using the interface to connect to the connectivity gateway. Themethod can also include mapping the tag to the at least one virtualnetwork.

In some embodiments of the method, mapping the tag to the at least oneVirtual networks, for each of the at least one Virtual networks,includes attaching a cloud gateway to the at least one virtual networkin the cloud environment. The method can also include saving an existingrouting table for the at least one virtual network. The method can alsoinclude creating a new routing table for the at least one virtualnetwork. The method can also include adding, to the new routing table, adefault route pointing to the cloud gateway. The method can also includeenabling route propagation based on the new routing table. The methodcan also include associating the cloud gateway to the connectivitygateway, wherein an advertised prefix list is set to an address prefixfor the at least one virtual network.

In some embodiments of the method, configuring the connection betweenthe at least one routing domain in the on-premises site and the at leastone virtual network can include providing a BGP configuration to theSDWAN router. The method can also include providing a segmentconfiguration to the SDWAN router. The method can also include providinga sub-interface configuration to the SDWAN router based on a virtuallocal area network (VLAN).

In some embodiments, the method also includes updating the tag. Themethod can also include automatically discovering connections affectedby the tag. The method can also include automatically discovering one ormore virtual networks on the cloud environment affected by the tag. Themethod can also include attaching a new cloud gateway to the one or morevirtual networks affected by the tag.

In some embodiments, the method also includes updating an existingrouting table for the one or more virtual networks affected by the tag.The method can also include enabling route propagation based on theexisting routing table. The method can also include attaching the newcloud gateway to an affected connectivity gateway belonging to theconnections affected by the tag and the one or more virtual networksaffected by the tag.

In some embodiments of the method, updating the tag includes adding oneor more new Virtual networks corresponding to the one or more virtualnetworks to the tag.

An example system can include one or more processors and at least onecomputer-readable storage medium storing instructions which, whenexecuted by the one or more processors, cause the one or more processorsto receive a tag associating at least one routing domain in anon-premises site with at least one virtual network in a cloudenvironment associated with a cloud service provider (CSP). Theinstructions can also cause the one or more processors to configure avirtual cross connect (VXC) on a software-defined wide-area network(SDWAN) router associated with a software-defined cloud infrastructure(SDCI) provider, the VXC connecting the on-premises site to the cloudenvironment associated with the CSP. The instructions can also cause theone or more processors to assign border gateway protocol (BGP)parameters to the VXC. The instructions can also cause the one or moreprocessors to configure BGP peering on a connectivity gateway in thecloud environment associated with the CSP. The instructions can alsocause the one or more processors to connect the connectivity gateway tothe at least one virtual network in the cloud environment. Theinstructions can also cause the one or more processors to tag the atleast one virtual network with the tag. The instructions can also causethe one or more processors to configure a connection between the atleast one routing domain in the on-premises site and the at least onevirtual network in the cloud environment, wherein the connection isbased at least in part on the tag.

An example non-transitory computer-readable storage medium having storedtherein instructions which, when executed by a processor, cause theprocessor to receive a tag associating at least one routing domain in anon-premises site with at least one virtual network in a cloudenvironment associated with a cloud service provider (CSP). Theinstructions can also cause the processor to configure a virtual crossconnect (VXC) on a software-defined wide-area network (SDWAN) routerassociated with a software-defined cloud infrastructure (SDCI) provider,the VXC connecting the on-premises site to the cloud environmentassociated with the CSP. The instructions can also cause the processorto assign border gateway protocol (BGP) parameters to the VXC. Theinstructions can also cause the processor to configure BGP peering on aconnectivity gateway in the cloud environment associated with the CSP.The instructions can also cause the processor to connect theconnectivity gateway to the at least one virtual network in the cloudenvironment. The instructions can also cause the processor to tag the atleast one virtual network with the tag. The instructions can also causethe processor to configure a connection between the at least one routingdomain in the on-premises site and the at least one virtual network inthe cloud environment, wherein the connection is based at least in parton the tag.

Example Embodiments

This disclosure will first discuss examples of network architectures andtopologies for software-defined wide-area networks (SD-WANs), as well asvarious overlays for such networks. Then, the disclosure will discussexample embodiments for automating connectivity to cloud resources.Finally, the disclosure will discuss an example computing system whichcan be used to execute the present technology.

FIG. 1 illustrates an example of a network architecture 100 forimplementing aspects of the present technology. An example of animplementation of the network architecture 100 is the Cisco® SD-WANarchitecture. However, one of ordinary skill in the art will understandthat, for the network architecture 100 and any other system discussed inthe present disclosure, there can be additional or fewer component insimilar or alternative configurations. The illustrations and examplesprovided in the present disclosure are for conciseness and clarity.Other embodiments may include different numbers and/or types of elementsbut one of ordinary skill the art will appreciate that such variationsdo not depart from the scope of the present disclosure.

In this example, the network architecture 100 can comprise anorchestration plane 102, a management plane 120, a control plane 130,and a data plane 140. The orchestration plane 102 can assist in theautomatic on-boarding of edge network devices 142 (e.g., switches,routers, etc.) in an overlay network. The orchestration plane 102 caninclude one or more physical or virtual network orchestrator appliances104. The network orchestrator appliance(s) 104 can perform the initialauthentication of the edge network devices 142 and orchestrateconnectivity between devices of the control plane 130 and the data plane140. In some embodiments, the network orchestrator appliance(s) 104 canalso enable communication of devices located behind Network AddressTranslation (NAT). In some embodiments, physical or virtual Cisco®SD-WAN vBond appliances can operate as the network orchestratorappliance(s) 104.

The management plane 120 can be responsible for central configurationand monitoring of a network. The management plane 120 can include one ormore physical or virtual network management appliances 122. In someembodiments, the network management appliance(s) 122 can providecentralized management of the network via a graphical user interface toenable a user to monitor, configure, and maintain the edge networkdevices 142 and links (e.g., Internet transport network 160, MPLSnetwork 162, 4G/LTE network 164) in an underlay and overlay network. Thenetwork management appliance(s) 122 can support multi-tenancy and enablecentralized management of logically isolated networks associated withdifferent entities (e.g., enterprises, divisions within enterprises,groups within divisions, etc.). Alternatively or in addition, thenetwork management appliance(s) 122 can be a dedicated networkmanagement system for a single entity. In some embodiments, physical orvirtual Cisco® SD-WAN vManage appliances can operate as the networkmanagement appliance(s) 122. The management plane 120 can include ananalytics engine 124 to provide analytics for the network.

The control plane 130 can build and maintain a network topology and makedecisions on where traffic flows. The control plane 130 can include oneor more physical or virtual network controller appliance(s) 132. Thenetwork controller appliance(s) 132 can establish secure connections toeach network device 142 and distribute route and policy information viaa control plane protocol (e.g., Overlay Management Protocol (OMP)(discussed in further detail below), Open Shortest Path First (OSPF),Intermediate System to Intermediate System (IS-IS), Border GatewayProtocol (BGP), Protocol-Independent Multicast (PIM), Internet GroupManagement Protocol (IGMP), Internet Control Message Protocol (ICMP),Address Resolution Protocol (ARP), Bidirectional Forwarding Detection(BFD), Link Aggregation Control Protocol (LACP), etc.). In someembodiments, the network controller appliance(s) 132 can operate asroute reflectors. The network controller appliance(s) 132 can alsoorchestrate secure connectivity in the data plane 140 between and amongthe edge network devices 142. For example, in some embodiments, thenetwork controller appliance(s) 132 can distribute crypto keyinformation among the network device(s) 142. This can allow the networkto support a secure network protocol or application (e.g., InternetProtocol Security (IPSec), Transport Layer Security (TLS), Secure Shell(SSH), etc.) without Internet Key Exchange (IKE) and enable scalabilityof the network. In some embodiments, physical or virtual Cisco® SD-WANvSmart controllers can operate as the network controller appliance(s)132.

The data plane 140 can be responsible for forwarding packets based ondecisions from the control plane 130. The data plane 140 can include theedge network devices 142, which can be physical or virtual networkdevices. The edge network devices 142 can operate at the edges variousnetwork environments of an organization, such as in one or more datacenters or colocation centers 150, campus networks 152, branch officenetworks 154, home office networks 154, and so forth, or in the cloud(e.g., Infrastructure as a Service (IaaS), Platform as a Service (PaaS),SaaS, and other cloud service provider networks). The edge networkdevices 142 can provide secure data plane connectivity among sites overone or more WAN transports, such as via one or more Internet transportnetworks 160 (e.g., Digital Subscriber Line (DSL), cable, etc.), MPLSnetworks 162 (or other private packet-switched network (e.g., MetroEthernet, Frame Relay, Asynchronous Transfer Mode (ATM), etc.), mobilenetworks 164 (e.g., 3G, 4G/LTE, 5G, etc.), or other WAN technology(e.g., Synchronous Optical Networking (SONET), Synchronous DigitalHierarchy (SDH), Dense Wavelength Division Multiplexing (DWDM), or otherfiber-optic technology; leased lines (e.g., T1/E1, T3/E3, etc.); PublicSwitched Telephone Network (PSTN), Integrated Services Digital Network(ISDN), or other private circuit-switched network; small apertureterminal (VSAT) or other satellite network; etc.). The edge networkdevices 142 can be responsible for traffic forwarding, security,encryption, quality of service (QoS), and routing (e.g., BGP, OSPF,etc.), among other tasks. In some embodiments, physical or virtualCisco® SD-WAN vEdge routers can operate as the edge network devices 142.

FIG. 2 illustrates an example of a network topology 200 for showingvarious aspects of the network architecture 100. The network topology200 can include a management network 202, a pair of network sites 204Aand 204B (collectively, 204) (e.g., the data center(s) 150, the campusnetwork(s) 152, the branch office network(s) 154, the home officenetwork(s) 156, cloud service provider network(s), etc.), and a pair ofInternet transport networks 160A and 160B (collectively, 160). Themanagement network 202 can include one or more network orchestratorappliances 104, one or more network management appliance 122, and one ormore network controller appliances 132. Although the management network202 is shown as a single network in this example, one of ordinary skillin the art will understand that each element of the management network202 can be distributed across any number of networks and/or beco-located with the sites 204. In this example, each element of themanagement network 202 can be reached through either transport network160A or 160B.

Each site can include one or more endpoints 206 connected to one or moresite network devices 208. The endpoints 206 can include general purposecomputing devices (e.g., servers, workstations, desktop computers,etc.), mobile computing devices (e.g., laptops, tablets, mobile phones,etc.), wearable devices (e.g., watches, glasses or other head-mounteddisplays (HMDs), ear devices, etc.), and so forth. The endpoints 206 canalso include Internet of Things (IoT) devices or equipment, such asagricultural equipment (e.g., livestock tracking and management systems,watering devices, unmanned aerial vehicles (UAVs), etc.); connected carsand other vehicles; smart home sensors and devices (e.g., alarm systems,security cameras, lighting, appliances, media players, HVAC equipment,utility meters, windows, automatic doors, door bells, locks, etc.);office equipment (e.g., desktop phones, copiers, fax machines, etc.);healthcare devices (e.g., pacemakers, biometric sensors, medicalequipment, etc.); industrial equipment (e.g., robots, factory machinery,construction equipment, industrial sensors, etc.); retail equipment(e.g., vending machines, point of sale (POS) devices, Radio FrequencyIdentification (RFID) tags, etc.); smart city devices (e.g., streetlamps, parking meters, waste management sensors, etc.); transportationand logistical equipment (e.g., turnstiles, rental car trackers,navigational devices, inventory monitors, etc.); and so forth.

The site network devices 208 can include physical or virtual switches,routers, and other network devices. Although the site 204A is shownincluding a pair of site network devices and the site 204B is shownincluding a single site network device in this example, the site networkdevices 208 can comprise any number of network devices in any networktopology, including multi-tier (e.g., core, distribution, and accesstiers), spine-and-leaf, mesh, tree, bus, hub and spoke, and so forth.For example, in some embodiments, one or more data center networks mayimplement the Cisco® Application Centric Infrastructure (ACI)architecture and/or one or more campus networks may implement the Cisco®Software Defined Access (SD-Access or SDA) architecture. The sitenetwork devices 208 can connect the endpoints 206 to one or more edgenetwork devices 142, and the edge network devices 142 can be used todirectly connect to the transport networks 160.

In some embodiments, “color” can be used to identify an individual WANtransport network, and different WAN transport networks may be assigneddifferent colors (e.g., mpls, private1, biz-internet, metro-ethernet,lte, etc.). In this example, the network topology 200 can utilize acolor called “biz-internet” for the Internet transport network 160A anda color called “public-internet” for the Internet transport network160B.

In some embodiments, each edge network device 208 can form a DatagramTransport Layer Security (DTLS) or TLS control connection to the networkcontroller appliance(s) 132 and connect to any network control appliance132 over each transport network 160. In some embodiments, the edgenetwork devices 142 can also securely connect to edge network devices inother sites via IPSec tunnels. In some embodiments, the BFD protocol maybe used within each of these tunnels to detect loss, latency, jitter,and path failures.

On the edge network devices 142, color can be used help to identify ordistinguish an individual WAN transport tunnel (e.g., no same color maybe used twice on a single edge network device). Colors by themselves canalso have significance. For example, the colors metro-ethernet, mpls,and private1, private2, private3, private4, private5, and private6 maybe considered private colors, which can be used for private networks orin places where there is no NAT addressing of the transport IP endpoints(e.g., because there may be no NAT between two endpoints of the samecolor). When the edge network devices 142 use a private color, they mayattempt to build IPSec tunnels to other edge network devices usingnative, private, underlay IP addresses. The public colors can include3g, biz, internet, blue, bronze, custom1, custom2, custom3, default,gold, green, lte, public-internet, red, and silver. The public colorsmay be used by the edge network devices 142 to build tunnels to post-NATIP addresses (if there is NAT involved). If the edge network devices 142use private colors and need NAT to communicate to other private colors,the carrier setting in the configuration can dictate whether the edgenetwork devices 142 use private or public IP addresses. Using thissetting, two private colors can establish a session when one or both areusing NAT.

FIG. 3 illustrates an example of a diagram 300 showing the operation ofOMP, which may be used in some embodiments to manage an overlay of anetwork (e.g., the network architecture 100). In this example, OMPmessages 302A and 302B (collectively, 302) may be transmitted back andforth between the network controller appliance 132 and the edge networkdevices 142A and 142B, respectively, where control plane information,such as route prefixes, next-hop routes, crypto keys, policyinformation, and so forth, can be exchanged over respective secure DTLSor TLS connections 304A and 304B. The network controller appliance 132can operate similarly to a route reflector. For example, the networkcontroller appliance 132 can receive routes from the edge networkdevices 142, process and apply any policies to them, and advertiseroutes to other edge network devices 142 in the overlay. If there is nopolicy defined, the edge network devices 142 may behave in a mannersimilar to a full mesh topology, where each edge network device 142 canconnect directly to another edge network device 142 at another site andreceive full routing information from each site.

OMP can advertise various types of routes. For example, OMP canadvertise OMP routes, which can correspond to prefixes that are learnedfrom the local site, or service side, of the edge network device 142.The prefixes can be originated as static or connected routes, or fromwithin, for example, the OSPF or BGP protocols, and redistributed intoOMP so they can be carried across the overlay. OMP routes can advertiseattributes such as transport location (TLOC) information (which cansimilar to a BGP next-hop IP address) and other attributes such asorigin, originator, preference, site identifier, tag, and virtualprivate network (VPN). An OMP route may be installed in the forwardingtable if the TLOC to which it points is active.

As another example, OMP can advertise TLOC routes, which can correspondto logical tunnel termination points on the edge network devices 142that connect into the transport networks 160. In some embodiments, aTLOC route can be uniquely identified and represented by a three-tuple,including an IP address, link color, and encapsulation (e.g., GenericRouting Encapsulation (GRE), IPSec, etc.). In addition to system IPaddress, color, and encapsulation, TLOC routes can also carry attributessuch as TLOC private and public IP addresses, carrier, preference, siteidentifier, tag, and weight. In some embodiments, a TLOC may be in anactive state on a particular edge network device 142 when an active BFDsession is associated with that TLOC.

As another example, OMP can advertise service routes, which canrepresent services (e.g., firewall, distributed denial of service (DDoS)mitigator, load balancer, intrusion prevent system (IPS), intrusiondetection systems (IDS), WAN optimizer, etc.) that may be connected tothe local sites of the edge network devices 142 and accessible to othersites for use with service insertion. In addition, these routes can alsoinclude VPNs; the VPN labels can be sent in an update type to tell thenetwork controller appliance 132 what VPNs are serviced at a remotesite.

In the example of FIG. 3 , OMP is shown running over the DTLS/TLStunnels 304 established between the edge network devices 142 and thenetwork controller appliance 132. In addition, the diagram 300 shows anIPSec tunnel 306A established between TLOC 308A and 308C over the WANtransport network 160A and an IPSec tunnel 306B established between TLOC308B and TLOC 308D over the WAN transport network 160B. Once the IPSectunnels 306A and 306B are established, BFD can be enabled across each ofthem.

FIG. 4 illustrates an example of a diagram 400 showing the operation ofVPNs, which may be used in some embodiments to provide segmentation fora network (e.g., the network architecture 100). VPNs can be isolatedfrom one another and can have their own forwarding tables. An interfaceor sub-interface can be explicitly configured under a single VPN and maynot be part of more than one VPN. Labels may be used in OMP routeattributes and in the packet encapsulation, which can identify the VPNto which a packet belongs. The VPN number can be a four-byte integerwith a value from 0 to 65530. In some embodiments, the networkorchestrator appliance(s) 104, network management appliance(s) 122,network controller appliance(s) 132, and/or edge network device(s) 142can each include a transport VPN 402 (e.g., VPN number 0) and amanagement VPN 404 (e.g., VPN number 512). The transport VPN 402 caninclude one or more physical or virtual network interfaces (e.g.,network interfaces 410A and 410B) that respectively connect to WANtransport networks (e.g., the MPLS network 162 and the Internettransport network 160). Secure DTLS/TLS connections to the networkcontroller appliance(s) 132 or between the network controllerappliance(s) 132 and the network orchestrator appliance(s) 104 can beinitiated from the transport VPN 402. In addition, static or defaultroutes or a dynamic routing protocol can be configured inside thetransport VPN 402 to get appropriate next-hop information so that thecontrol plane 130 may be established and IPSec tunnels 306 (not shown)can connect to remote sites.

The management VPN 404 can carry out-of-band management traffic to andfrom the network orchestrator appliance(s) 104, network managementappliance(s) 122, network controller appliance(s) 132, and/or edgenetwork device(s) 142 over a network interface 410C. In someembodiments, the management VPN 404 may not be carried across theoverlay network.

In addition to the transport VPN 402 and the management VPN 404, thenetwork orchestrator appliance(s) 104, network management appliance(s)122, network controller appliance(s) 132, or edge network device(s) 142can also include one or more service-side VPNs 406. The service-side VPN406 can include one or more physical or virtual network interfaces(e.g., network interfaces 410D and 410E) that connect to one or morelocal-site networks 412 and carry user data traffic. The service-sideVPN(s) 406 can be enabled for features such as OSPF or BGP, VirtualRouter Redundancy Protocol (VRRP), QoS, traffic shaping, policing, andso forth. In some embodiments, user traffic can be directed over IPSectunnels to other sites by redistributing OMP routes received from thenetwork controller appliance(s) 132 at the site 412 into theservice-side VPN routing protocol. In turn, routes from the local site412 can be advertised to other sites by advertising the service VPNroutes into the OMP routing protocol, which can be sent to the networkcontroller appliance(s) 132 and redistributed to other edge networkdevices 142 in the network. Although the network interfaces 410A-E(collectively, 410) are shown to be physical interfaces in this example,one of ordinary skill in the art will appreciate that the interfaces 410in the transport and service VPNs can also be sub-interfaces instead.

Now the disclosure turns to discussing examples for automatingconnectivity to cloud resources. The present technology can utilize thetools available in SDWAN networks, as described in FIGS. 1-4 , toautomate intent-driven connectivity from on-premises network segments tocloud resources. By automatically and dynamically mapping on-premisesnetwork segments to cloud resources, workload on network administratorscan be reduced, high uptime can be preserved, and service-levelagreements throughout the connectivity chain can be preserved. Thisfills a need in the art by dynamically mapping cloud resources tonetwork segments of network sites such as on-premises networks.

FIG. 5 illustrates an example of a network capable of automatingconnectivity to cloud resources. Network controller 500 can sendrequests to connectivity gateway 530 and interconnect gateway 550 thatconnect any of segments 570-1, 570-2, or 570-3 to any of virtualnetworks 520-1, 520-2, or 520-3.

Network controller 500 can be a network controller similar to networkcontroller appliance(s) 132 illustrated in FIG. 1 . For example, networkcontroller 500 can be a controller utilizing CISCO vManage. Networkcontroller 500 can send requests and configurations to connectivitygateway 530 and interconnect gateway 550. For example, a configurationsent to interconnect gateway 550 can include a configuration toestablish a border gateway protocol (BGP), a configuration for a networksegment, or a configuration for a sub-interface based on VLAN.

SDWAN fabric 560 can be a network similar to data center 150, campus152, branch office 154, or home office 156 illustrated in FIG. 1 ornetworks 204A and 204B illustrated in FIG. 2 . SDWAN fabric 560 can bean on-premises network containing segments 570-1, 570-2, and 570-3(collectively segments 570). For example, segments 570 can be virtualrouting functions.

SDCI network 540 can be a software-defined cloud infrastructure (SDCI)network. SDCI network 540 can be similar to data center 150, campus 152,branch office 154, or home office 156 illustrated in FIG. 1 or networks204A and 204B illustrated in FIG. 2 . SDCI network 540 can act as anintermediary network between SDWAN fabric 560 and cloud environment 510.

Cloud environment 510 can be a network similar to networks 204A and 204Billustrated in FIG. 2 . Cloud environment 510 can contain virtualnetworks 520-1, 520-2, and 520-3 (collectively “virtual networks 520”hereinafter).

Interconnect gateway 550 and connectivity gateway 530 can be routers ornetwork edges. Interconnect gateway 550 can connect SDWAN fabric 560 toSDCI network 540. Connectivity gateway 530 can connect SDCI network 540to cloud environment 510.

For example, cloud environment 510 can be Amazon Web Services, virtualnetworks 520 can be virtual private clouds, and connectivity gateway 530can be a direct connect gateway. In another example, cloud environment510 can be Google Cloud, virtual networks 520 can be virtual privateclouds, and connectivity gateway 530 can be a Google cloud router.

Network controller 500 can setup connectivity between a segment 570 anda virtual network 520. This connectivity can be enabled by tags receivedby network controller 500 indicating that a connection between a segment570 and a virtual network 520 should be established. For example, thetags can map or associate a segment (e.g., a virtual network, a routingdomain, a prefix, a subnet, etc.) of the SDWAN fabric 560 to a virtualnetwork (e.g., a virtual private network or routing domain, etc.) in thecloud environment 510, which can be used to establish connectivitybetween the segment in the SDWAN fabric 560 and the virtual network inthe cloud environment 510. In some examples, a tag can associated asegment(s) and a virtual network based on one or more factors such as,for example and without limitation, a common attribute (e.g., a commonservice or functionality, a common set of associatedusers/groups/devices, a common security group or policy, a common set ofrequirements, etc.), a relationship, a preference, etc. These tags canbe received from a network administrator, an automated process, or viaother means.

To achieve connectivity between a segment 570 and a virtual network 520,network controller can send requests and configurations to interconnectgateway 550 and connectivity gateway 530. Network controller 500 canestablish connectivity between interconnect gateway 550 and connectivitygateway 530 and between connectivity gateway 530 and a virtual network520. Taken together, network controller 500 can establish connectivitybetween a segment 570 and a virtual network 520, as a segment 570 isalready connected to interconnect gateway 550.

Network controller 500 can establish connectivity between interconnectgateway 550 and connectivity gateway 530. In some examples, thisconnectivity can be a virtual cross connect (VXC). A VXC is a layer 2connection, or data link layer connection, originating in interconnectgateway 550 and extending to connectivity gateway 530.

Network controller 500 can build the VXC and send it to interconnectgateway 550 on SDCI network 540. Below is an example of code forbuilding a VXC on interconnect gateway 550, which network controller 500can send to interconnect gateway 550:

-   -   a_end={ }    -   a_end[‘vlan’]=0    -   a_end[‘innerVlan’]=0    -   b_end={ }    -   b_end[‘productUid’]=destinationProductId #Partner port Location        Id    -   b_end[‘vlan’]=0    -   b_end[‘innerVlan’]=0    -   cloud_vxc_req[‘productUid’]=sourceProductId #MVE Product d    -   associated_vxcs={ }    -   associated_vxcs[‘productName’]=connectivityName #Name of the        connection    -   associated_vxcs[‘rateLimit’]=connectivitySpeed #Speed of the        connection    -   associated_vxcs[‘aEnd’]=a_end    -   associated_vxcs[‘bEnd’]=b_end    -   associated_vxcs_array=[ ]    -   associated_vxcs_array.apperid(associated_vxcs)    -   cloud_vxc_req[‘associatedVxcs’]=associated_vxcS_array    -   create_vxc_array=[ ]    -   create_vxc_array.append(cloud_vxc_req)

Once interconnect gateway 550 has received the VXC, SDCI network 540 canvalidate the VXC creation request. A network administrator operatingnetwork controller 500 can validate the request, or the request can bevalidated in an automated manner, or via other means.

Network controller 500 can establish connectivity between interconnectgateway 550 and virtual network(s) 520 via connectivity gateway 530.Virtual networks 520 can be specified by the tag received by networkcontroller 500.

Network controller 500 can invoke an API to request connectivity gateway530 to accept a virtual interface for SDCI network 540. For example,when cloud environment 510 is Amazon Web Services, the virtual interfacecan be a private or transit virtual interface. In another example, whencloud environment 510 is Google Cloud, the virtual interface can be apartner interconnect. Below is an example of code for askingconnectivity gateway 530 to accept a virtual interface for SDCI network540, which network controller 500 can send to connectivity gateway 530:

-   -   response=self.get_dc_client(        ).confirm_private_virtual_interface(virtualInterfaceid=vif_id,        threctConnectGatewayId=dcg_id)

Using this virtual interface, network controller 500 can map virtualnetworks specified in the tag to the set of virtual networks 520. Forexample, to achieve this when cloud environment 510 is Amazon WebServices, for each virtual network 520, network controller 500 can:

-   -   1) Create a virtual private gateway and attach it to virtual        network 520:        -   response=self.get_ec2_client(            ).create_vpn_gateway(Type=vpg_type, AmazonSideAsn=asn.            DryRun=False)        -   response=self.get_ec2_client(            ).attach_vpn_gateway(VpcId=vpc_id, VpnGatewayId=vpg_id)    -   2) Save an existing routing table for virtual network 520 and        create a new routing table for virtual network 520:        -   #Build the tag specifications.        -   tag_list=[{‘Key’: route_table_fields[‘name’], ‘Value’:            name}]        -   tag_specifications=[        -   {        -   ‘ResourceType’: ‘route-table’,        -   ‘Tags’: tag_list,        -   }        -   ]        -   response=self.get_ec2_client(            ).create_route_table(VpcId=vpc_id,            TagSpecifications=tag_specifications)    -   3) Add a default route to the new routing table pointing to the        virtual private gateway:        -   ret_code=self.get_ec2_client(            ).create_route(DestinationCidrBlock=cidr_block,            GatewayId—gw_id,        -   RouteTableId=route_table_id)        -   response=self.get_ec2_clientt(            ).replace_route_table_association(ssociationId=old_association_id,        -   RouteTableId=new_route_table_id)    -   4) Associate the virtual private gateway with connectivity        gateway 530, where the advertised prefix list is set to the        address prefix for virtual network 520:        -   response=self.get_dc_client(            ).create_direct_connect_gateway_association(directConnectGatewayId=dcg_i            d,        -   gatewayId=gw_id,        -   addAllowcdPrefixesToDirectConnectGateway=advertised_prefix_list)

In some cases, to complete the connection from segment 570 to virtualnetwork 520, network controller 500 can push configurations tointerconnect gateway 550. Network controller 500 can configure bordergateway protocol (BGP) peering between interconnect gateway 550 andvirtual network 520. Network connection 500 can push variousconfigurations to interconnect gateway 550 to establish BGP peering,including:

  1) BGP peering configurations  vrf definition 18   rd 1:1  address-family ipv4   route-target export 65080:1   route-targetimport 65080:1   exit-address-family   !   address-family ipv6  exit-address-family   !  1 2) Segment configurations:  interfaceGigabitEthernet1.2936   no shutdown   encapsulation dot1Q 2.936   vrfforwarding 10   ip address 192.168.8.29 255.255.255.252   ip mtu 1496 exit 3) Virtual network sub-interface configurations  router bgp 65000  bgp log-neighbor-changes   address-family ipv4 unicast vrf 10  distance bgp 28 200 20   neighbor 192.168.0.30 remote-as 64515  neighbor 192.168.0.30 activate   neighbor 192.168.0.30 activate  neighbor 192.168.0.30 description test-tgw-asn   neighbor 192.168.0.30ebgp-multihop   neighbor 192.168.0.30 password 0 ECLZMNSMSXGDV65IZGM5  neighbor 192.168.0.30 send-community both   redistribute omp  exit-address-family   !   timers bgp 68 180  !

In some examples, a tag governing connections between SDWAN fabric 560and cloud environment 510 can be updated. Network controller 500 canautomatically discover connections affected by the tag as well asendpoints in segments 570 and virtual networks 520 and apply the tagchanges accordingly. For example, when cloud environment 510 is AmazonWeb Services, network controller 500 can attach a new virtual cloudgateway to the affected virtual networks 520 and connectivity gateway530, and update the routing table for virtual networks 520.

FIGS. 6A-6C illustrate examples of graphical user interfaces (GUIs) fornetwork controller 500 as illustrated in FIG. 5 . Through these GUIs, anetwork administrator can discover virtual networks 520, add tags tovirtual networks 520, or edit tags for virtual networks 520.

FIG. 6A illustrates a GUI 610 for discovering virtual networks 520.After cloud environment 510 is associated with network controller 500,network controller 500 can sync all virtual networks 520 from respectiveaccounts and display them. GUI 610 can display information such as thename of cloud environment 510, and for each virtual network 520 candisplay cloud region, account name, the host virtual network name, thehost virtual network tab, whether the virtual network is interconnectenabled, the account ID, and the host virtual network ID. A networkadministrator can, using GUI 610, select multiple virtual networks 520across multiple cloud environments 510 and group them as a singlelogical group known as a tag. This tag acts as single control point forall virtual networks 520 associated with the tag.

FIG. 6B illustrates a GUI 620 for creating a tag. A networkadministrator can specify a tag name and select virtual networks 520 ina given region. The network administrator can choose whether to enableinterconnect connectivity for the new tag. A tag, once created, can beassociated to a connection as part of an interconnect connectioncreation to establish connectivity from segments 570 to virtual networks520.

FIG. 6C illustrates a GUI 630 for editing a tag. A network administratorcan modify the composition of already-deployed tags at a later point toupdate virtual networks 520 associated with the tags. If such amodification is made, network controller 500 can detect and adjust theconnectivity accordingly.

FIG. 7 illustrates an example method 700 for automating connectivity tocloud resources. Although the example method 700 depicts a particularsequence of operations, the sequence may be altered without departingfrom the scope of the present disclosure. For example, some of theoperations depicted may be performed in parallel or in a differentsequence that does not materially affect the function of the method 700.In other examples, different components of an example device or systemthat implements the method 700 may perform functions at substantiallythe same time or in a specific sequence.

At block 710, the method 700 includes receiving a tag associating atleast one routing domain in an on-premises site with at least onevirtual network in a cloud environment associated with a cloud serviceprovider (CSP). For example, network controller 500 illustrated in FIG.5 may receive a tag associating at least one routing domain in anon-premises site with at least one virtual network in a cloudenvironment associated with a CSP.

At block 720, the method 700 includes configuring a virtual crossconnect (VXC) on a software-defined wide-area network (SDWAN) routerassociated with a software-defined cloud infrastructure provider (SDCI),the VXC connecting the on-premises site to the cloud environmentassociated with the CSP. For example, network controller 500 illustratedin FIG. 5 may establish a VXC on an SDWAN router associated with an SDCIprovider, the VXC connecting the on-premises site to the cloudenvironment associated with the CSP.

At block 730, the method 700 includes assigning border gateway protocol(BGP) parameters to the VXC. For example, network controller 500illustrated in FIG. 5 may assign BGP parameters to the VXC.

At block 740, the method 700 includes configuring BGP peering on aconnectivity gateway in the cloud environment associated with the CSP.For example, network controller 500 illustrated in FIG. 5 may configureBGP peering on a connectivity gateway in the cloud environmentassociated with the CSP.

At block 750, the method 700 includes connecting the connectivitygateway to the at least one virtual network in the cloud environment.For example, network controller 500 illustrated in FIG. 5 may connectthe connectivity gateway to the at least one virtual network in thecloud environment.

In another example of connecting the connectivity gateway to the atleast one virtual network in the cloud environment at block 750, themethod 700 can include invoking an API to use an interface associatedwith the SDCI provider. Further, the method 700 can include using theinterface to connect to the connectivity gateway. Further, the method700 can include mapping the tag to the at least one virtual network.

In another example of the mapping the tag, the method 700 can includeattaching a cloud gateway to the at least one virtual network in thecloud environment. Further, the method 700 can include saving anexisting routing table for the at least one virtual network. Further,the method 700 can include creating a new routing table for the at leastone virtual network. Further, the method 700 can include adding, to thenew routing table, a default route pointing to the cloud gateway.Further, the method 700 can include enabling route propagation based onthe new routing table. Further, the method 700 can include associatingthe cloud gateway to the connectivity gateway. In some examples, anadvertised prefix list is set to an address prefix for the at least onevirtual network.

At block 760, the method 700 includes tagging the at least one virtualnetwork with the tag. For example, network controller 500 illustrated inFIG. 5 may tag the at least one virtual network with the tag.

At block 770, the method 700 includes establishing a connection betweenthe at least one routing domain in the on-premises site and the at leastone virtual network in the cloud environment. For example, networkcontroller 500 illustrated in FIG. 5 may establish a connection betweenthe at least one routing domain in the on-premises site and the at leastone virtual network in the cloud environment. In some examples, theconnection is based at least in part on the tag.

In another example of the establishing a connection at block 770, themethod 700 can include providing a BGP configuration to the SDWANrouter. Further, the method 700 can include providing a segmentconfiguration to the SDWAN router. Further, the method 700 can includeproviding a sub-interface configuration to the SDWAN router based on avirtual local area network.

In some embodiments, the method 700 can also include updating the tag.For example, network controller 500 illustrated in FIG. 5 can update thetag. Further, the method 700 can include automatically discoveringconnections affected by the tag. Further, the method 700 can includeautomatically discovering one or more virtual networks on the cloudenvironment affected by the tag. Further, the method 700 can includeattaching a new cloud gateway to the one or more virtual networksaffected by the tag. In some examples, updating the tag includes addingone or more new Virtual networks corresponding to the one or morevirtual networks to the tag.

In some embodiments, the method 700 can also include updating anexisting routing table for the one or more virtual networks affected bythe tag. For example, network controller 500 illustrated in FIG. 5 canupdate an existing routing table for the one or more virtual networksaffected by the tag. Further, the method 700 can include enabling routepropagation based on the existing routing table. Further, the method 700can include attaching the new cloud gateway to an affected connectivitygateway belonging to the connections affected by the tag and the one ormore virtual networks affected by the tag.

FIG. 8 shows an example of computing system 800, which can be forexample any computing device making up network controller 500 or anycomponent thereof in which the components of the system are incommunication with each other using connection 805. Connection 805 canbe a physical connection via a bus, or a direct connection intoprocessor 810, such as in a chipset architecture. Connection 805 canalso be a virtual connection, networked connection, or logicalconnection.

In some embodiments, computing system 800 is a distributed system inwhich the functions described in this disclosure can be distributedwithin a datacenter, multiple data centers, a peer network, etc. In someembodiments, one or more of the described system components representsmany such components each performing some or all of the function forwhich the component is described. In some embodiments, the componentscan be physical or virtual devices.

Example system 800 includes at least one processing unit (CPU orprocessor) 810 and connection 805 that couples various system componentsincluding system memory 815, such as read-only memory (ROM) 820 andrandom access memory (RAM) 825 to processor 810. Computing system 800can include a cache of high-speed memory 812 connected directly with, inclose proximity to, or integrated as part of processor 810.

Processor 810 can include any general purpose processor and a hardwareservice or software service, such as services 832, 834, and 836 storedin storage device 830, configured to control processor 810 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. Processor 810 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction, computing system 800 includes an inputdevice 845, which can represent any number of input mechanisms, such asa microphone for speech, a touch-sensitive screen for gesture orgraphical input, keyboard, mouse, motion input, speech, etc. Computingsystem 800 can also include output device 835, which can be one or moreof a number of output mechanisms known to those of skill in the art. Insome instances, multimodal systems can enable a user to provide multipletypes of input/output to communicate with computing system 800.Computing system 800 can include communications interface 840, which cangenerally govern and manage the user input and system output. There isno restriction on operating on any particular hardware arrangement, andtherefore the basic features here may easily be substituted for improvedhardware or firmware arrangements as they are developed.

Storage device 830 can be a non-volatile memory device and can be a harddisk or other types of computer readable media which can store data thatare accessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs), read-only memory (ROM), and/or somecombination of these devices.

The storage device 830 can include software services, servers, services,etc., that when the code that defines such software is executed by theprocessor 810, it causes the system to perform a function. In someembodiments, a hardware service that performs a particular function caninclude the software component stored in a computer-readable medium inconnection with the necessary hardware components, such as processor810, connection 805, output device 835, etc., to carry out the function.

For clarity of explanation, in some instances, the present technologymay be presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware services or services, alone or in combination with otherdevices. In some embodiments, a service can be software that resides inmemory of a client device and/or one or more servers of a contentmanagement system and perform one or more functions when a processorexecutes the software associated with the service. In some embodiments,a service is a program or a collection of programs that carry out aspecific function. In some embodiments, a service can be considered aserver. The memory can be a non-transitory computer-readable medium.

In some embodiments, the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer-readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The executable computer instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, solid-state memory devices, flash memory, USB devices providedwith non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include servers,laptops, smartphones, small form factor personal computers, personaldigital assistants, and so on. The functionality described herein alsocan be embodied in peripherals or add-in cards. Such functionality canalso be implemented on a circuit board among different chips ordifferent processes executing in a single device, by way of furtherexample.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

What is claimed is:
 1. A method comprising: receiving a tag associatingat least one routing domain in an on-premises site with at least onevirtual network in a cloud environment associated with a cloud serviceprovider (CSP); automatically configuring a virtual cross connect (VXC)on a software-defined wide-area network (SDWAN) router associated with asoftware-defined cloud infrastructure (SDCI) provider, the VXCconnecting the on-premises site to the cloud environment associated withthe CSP; connecting a connectivity gateway in the cloud environmentassociated with the CSP to the at least one virtual network in the cloudenvironment; tagging the at least one virtual network with the tag; andconfiguring a connection between the at least one routing domain in theon-premises site and the at least one virtual network in the cloudenvironment, wherein the connection is based at least in part on thetag.
 2. The method of claim 1, wherein connecting the connectivitygateway to the at least one virtual network comprises: invoking an APIto use an interface associated with the SDCI provider; using theinterface to connect to the connectivity gateway; and mapping the tag tothe at least one virtual network.
 3. The method of claim 2, whereinmapping the tag to the at least one Virtual networks, for each of the atleast one Virtual networks, comprises: attaching a cloud gateway to theat least one virtual network in the cloud environment; saving anexisting routing table for the at least one virtual network; creating anew routing table for the at least one virtual network; adding, to thenew routing table, a default route pointing to the cloud gateway;enabling route propagation based on the new routing table; andassociating the cloud gateway to the connectivity gateway, wherein anadvertised prefix list is set to an address prefix for the at least onevirtual network.
 4. The method of claim 1, wherein configuring theconnection between the at least one routing domain in the on-premisessite and the at least one virtual network comprises: providing a bordergateway protocol configuration to the SDWAN router; providing a segmentconfiguration to the SDWAN router; and providing a sub-interfaceconfiguration to the SDWAN router based on a virtual local area network(VLAN).
 5. The method of claim 1, further comprising: updating the tag;automatically discovering connections affected by the tag; automaticallydiscovering one or more virtual networks on the cloud environmentaffected by the tag; and attaching a new cloud gateway to the one ormore virtual networks affected by the tag.
 6. The method of claim 5,further comprising: updating an existing routing table for the one ormore virtual networks affected by the tag; enabling route propagationbased on the existing routing table; and attaching the new cloud gatewayto an affected connectivity gateway belonging to the connectionsaffected by the tag and the one or more virtual networks affected by thetag.
 7. The method of claim 5, wherein updating the tag comprises addingone or more new Virtual networks corresponding to the one or morevirtual networks to the tag.
 8. A system comprising: one or moreprocessors; and at least one computer-readable storage medium storinginstructions which, when executed by the one or more processors, causethe one or more processors to: receive a tag associating at least onerouting domain in an on-premises site with at least one virtual networkin a cloud environment associated with a cloud service provider (CSP);automatically configure a virtual cross connect (VXC) on asoftware-defined wide-area network (SDWAN) router associated with asoftware-defined cloud infrastructure (SDCI) provider, the VXCconnecting the on-premises site to the cloud environment associated withthe CSP; connect a connectivity gateway in the cloud environmentassociated with the CSP to the at least one virtual network in the cloudenvironment; tag the at least one virtual network with the tag; andconfigure a connection between the at least one routing domain in theon-premises site and the at least one virtual network in the cloudenvironment, wherein the connection is based at least in part on thetag.
 9. The system of claim 8, wherein the instructions for connectingthe connectivity gateway to the at least one virtual network are furthereffective to cause the one or more processors to: invoke an API to usean interface associated with the SDCI provider; use the interface toconnect to the connectivity gateway; and map the tag to the at least onevirtual network.
 10. The system of claim 9, wherein the instructions formapping the tag to the at least one Virtual networks, for each of the atleast one Virtual networks are further effective to cause the one ormore processors to: attach a cloud gateway to the at least one virtualnetwork in the cloud environment; save an existing routing table for theat least one virtual network; create a new routing table for the atleast one virtual network; add, to the new routing table, a defaultroute pointing to the cloud gateway; enable route propagation based onthe new routing table; and associate the cloud gateway to theconnectivity gateway, wherein an advertised prefix list is set to anaddress prefix for the at least one virtual network.
 11. The system ofclaim 8, wherein the instructions for configuring the connection betweenthe at least one routing domain in the on-premises site and the at leastone virtual network are further effective to cause the one or moreprocessors to: provide a border gateway protocol configuration to theSDWAN router; provide a segment configuration to the SDWAN router; andprovide a sub-interface configuration to the SDWAN router based on avirtual local area network (VLAN).
 12. The system of claim 8, whereinthe instructions are further effective to cause the one or moreprocessors to: update the tag; automatically discover connectionsaffected by the tag; automatically discover one or more virtual networkson the cloud environment affected by the tag; and attach a new cloudgateway to the one or more virtual networks affected by the tag.
 13. Thesystem of claim 12, wherein the instructions are further effective tocause the one or more processors to: update an existing routing tablefor the one or more virtual networks affected by the tag; enable routepropagation based on the existing routing table; and attach the newcloud gateway to an affected connectivity gateway belonging to theconnections affected by the tag and the one or more virtual networksaffected by the tag.
 14. The system of claim 12, wherein theinstructions for updating the tag are further effective to cause the oneor more processors to add one or more new Virtual networks correspondingto the one or more virtual networks to the tag.
 15. A non-transitorycomputer-readable storage medium having stored therein instructionswhich, when executed by a processor, cause the processor to: receive atag associating at least one routing domain in an on-premises site withat least one virtual network in a cloud environment associated with acloud service provider (CSP); automatically configure a virtual crossconnect (VXC) on a software-defined wide-area network (SDWAN) routerassociated with a software-defined cloud infrastructure (SDCI) provider,the VXC connecting the on-premises site to the cloud environmentassociated with the CSP; connect a connectivity gateway in the cloudenvironment associated with the CSP to the at least one virtual networkin the cloud environment; tag the at least one virtual network with thetag; and configure a connection between the at least one routing domainin the on-premises site and the at least one virtual network in thecloud environment, wherein the connection is based at least in part onthe tag.
 16. The non-transitory computer-readable storage medium ofclaim 15, wherein the instructions for connecting the connectivitygateway to the at least one virtual network are further effective tocause the processor to: invoke an API to use an interface associatedwith the SDCI provider; use the interface to connect to the connectivitygateway; and map the tag to the at least one virtual network.
 17. Thenon-transitory computer-readable medium of claim 16, wherein theinstructions for mapping the tag to the at least one Virtual networks,for each of the at least one Virtual networks are further effective tocause the processor to: attach a cloud gateway to the at least onevirtual network in the cloud environment; save an existing routing tablefor the at least one virtual network; create a new routing table for theat least one virtual network; add, to the new routing table, a defaultroute pointing to the cloud gateway; enable route propagation based onthe new routing table; and associate the cloud gateway to theconnectivity gateway, wherein an advertised prefix list is set to anaddress prefix for the at least one virtual network.
 18. Thenon-transitory computer-readable storage medium of claim 15, wherein theinstructions for configuring the connection between the at least onerouting domain in the on-premises site and the at least one virtualnetwork are further effective to cause the processor to: provide aborder gateway protocol configuration to the SDWAN router; provide asegment configuration to the SDWAN router; and provide a sub-interfaceconfiguration to the SDWAN router based on a virtual local area network(VLAN).
 19. The non-transitory computer-readable storage medium of claim15, wherein the instructions are further effective to cause theprocessor to: update the tag; automatically discover connectionsaffected by the tag; automatically discover one or more virtual networkson the cloud environment affected by the tag; and attach a new cloudgateway to the one or more virtual networks affected by the tag.
 20. Thenon-transitory computer-readable storage medium of claim 19, wherein theinstructions are further effective to cause the processor to: update anexisting routing table for the one or more virtual networks affected bythe tag; enable route propagation based on the existing routing table;and attach the new cloud gateway to an affected connectivity gatewaybelonging to the connections affected by the tag and the one or morevirtual networks affected by the tag.